home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 2001 May
/
SGI IRIX Base Documentation 2001 May.iso
/
usr
/
relnotes
/
inventor_eoe
/
ch3.z
/
ch3
Wrap
Text File
|
2001-04-17
|
3KB
|
133 lines
- 1 -
3. _N_e_w__F_e_a_t_u_r_e_s__i_n__2_._1
This chapter describes the changes and additions to Open
Inventor 2.1.6 since Open Inventor 2.1/2.1.1, that are of
interest to end users. See the Release Notes for the Open
Inventor Development Kit (inventor_dev.man.relnotes) for a
complete list of new and changed features in the toolkit.
_M_u_l_t_i_p_l_e _v_e_r_s_i_o_n_s _o_f _t_h_e _l_i_b_r_a_r_i_e_s
Open Inventor 2.1.2 introduced the sw32.lib and sw64.lib
subsystems. The sw32.lib subsystem has been merged with
the sw.lib subsystem for 2.1.6. The sw64.lib subsystem
contains library versions corresponding to the application
binary interfaces (ABIs) supported by the IRIX 6.5
compilers and tools. It need only be installed if you
have applications compiled for the 64-bit ABI.
_I_n_t_e_r_n_a_t_i_o_n_a_l _t_e_x_t _i_n _t_h_e _s_c_e_n_e
This release of Open Inventor has support for two-
dimensional and three-dimensional international text in
Inventor scenes. This capability results from two changes
in Inventor:
1. The SoMFField "string" in SoText2 and SoText3 nodes
is now regarded as a UTF-8 character string. Ascii
is a subset of UTF-8, so existing ascii strings in
SoText2 and SoText3 nodes will continue to display
correctly. In addition, UTF-8 can be used to encode
various characters of international text, permitting
any such text to appear in SoText2 or SoText3 nodes.
2. The name field in SoFont nodes formerly could only
contain one font name. Now it may contain a
semicolon-separated list of font names. By using
multiple fonts in the same SoFont node, multiple
international characters sets can be used in the
same SoText2 or SoText3 node. When a character in
an SoText2 or SoText3 string is translated, the list
of fonts in the state is used to determine how to
render the character. The character will be
rendered according to the first font (in the list of
font names in the state) that contains the specified
character.
- 2 -
In some cases Inventor 2.0 files have used the string
field of SoText2 and SoText3 nodes to contain nonascii
characters, for example to represent nonascii characters
in Latin text such as accented letters. These characters
can no longer be used in string fields of Inventor 2.1
text nodes. These character strings in Inventor 2.0 files
will be automatically converted to their UTF-8 equivalents
when read by Inventor 2.1.2 and 2.1.3 applications.